-
Notifications
You must be signed in to change notification settings - Fork 256
Improves DX for containers #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors the spec-workflow-mcp container setup to use runtime user/group ID mapping via the --user flag, replacing the previous build-time user configuration. The changes include a new automated setup script, updated documentation, and Dockerfile modifications to support this new approach.
Key changes:
- Introduces an automated setup script (
setup-mcp.sh) that detects user/group IDs and configures.mcp.jsonautomatically - Updates Dockerfile to make application files world-readable and removes fixed user configuration, enabling runtime user mapping
- Updates documentation to reflect the new configuration approach with full project directory mounting
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| containers/setup-mcp.sh | New automated setup script that configures .mcp.json with proper user/group IDs and manages .spec-workflow directory permissions |
| containers/README.md | Updated documentation to include automated setup instructions and clarify the new runtime user mapping approach |
| containers/Dockerfile | Modified to remove fixed user configuration, make files world-readable, and support runtime --user flag usage |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
The previous implementation had permissions issues in some scenarios and wasn't portable.
This PR introduces a shell script for adding the docker container to
.mcp.jsonby manipulating an existing file, or creating a new.mcp.jsonfile. The script is run in the project directory and determines the correct uid and gid for the container to run and all the necessary paths.The user cd's to their project directory runs, e.g.
~/spec-workflow-mcp/containers/setup-mcp.shand they should be good to go.I've been using this successfully for a week or so. Works well in my experience.